Would like to see some good practices for organaizing structs / code / files when there are a bunch of queries that shares similiar shapes and how to organize all structs which describes return types (derived from Queryable).

Would like to see some good practices for organaizing structs / code / files when there are a bunch of queries that shares similiar shapes and how to organize all structs which describes return types (derived from Queryable).

Something really comprehensive might turn this from a quick guide into something else but have added two tips off the top of my head that fit with the Open-Meteo output:

1cc57b0

Let's say I want to return Json directly without using serde. How can I do it?
How to convert edgedb_protocol::model::Json to axum::Json?

impl IntoResponse for edb_model::Json {
   fn into_response(self) -> axum::response::Response {
      (
         [(
            axum::http::header::CONTENT_TYPE,
            "application/json".parse::<axum::http::HeaderValue>().unwrap(),
         )],
         self.to_string(),
      )
   }
}

only traits defined in the current crate can be implemented for types defined outside of the crate

Something like this can help:

struct EdgedbJson(edb_model::Json);
impl IntoResponse for EdgedbJson {
   fn into_response(self) -> axum::response::Response {
      let mut response = Response::new(self.0.to_string().into());
      response.headers_mut().append(
         axum::http::header::CONTENT_TYPE,
         "application/json".parse::<axum::http::HeaderValue>().unwrap(),
      );
      response
   }
}